A few conclusions worth internalising before you design permissions for your

own node.

Do not treat an allow list as a login. It is closer to a door that only opens

while you happen to be holding a specific key in a specific hand. The moment

the link drops, the key is gone. That is fine for a page you rarely need and

can afford to re-identify for. It is painful for an operations page you reach

for precisely when something has gone wrong - which is usually just after a

restart.

Restarting the node logs everyone out, including you. Worth remembering that

NomadNet registers its page handlers once at startup, so adding or renaming a

page requires a restart, and that restart drops every identification along with

it. Editing the contents of a page that already exists does not.

Anonymous is not the same as hostile. Most callers on a mesh are anonymous

simply because that is the default and they never had a reason to change it.

Design public pages to work well for someone you know nothing about.

If a page must be reachable, give it a second door. Accept an allow-listed

identity, and also accept something that survives a reconnect: a password, or a

session token carried in the page link. Identity is the convenient path when it

works; the other door is what stops you being locked out of your own node.

And whatever you build, put the sensitive parts outside the pages directory.

NomadNet serves every file it finds under that directory, not only .mu pages.

<- Prev Chapter Next Chapter ->